Add project setting toggle using the new SettingRow pattern component.
When enabled, users must assign at least one owner when creating a
feature flag.

- Add require_feature_owners to Project type and UpdateProjectBody
- Create RequireFeatureOwnershipSetting using SettingRow
- Add to Additional Settings section

Note: backend field does not exist yet — frontend is ready for when
the API adds the require_feature_owners field to the Project model.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Generic Skeleton component wrapping the existing .skeleton CSS classes.
Three variants: text (default), badge (pill), circle (avatar/icon).

Stories include:
- Interactive playground with controls
- All variants with descriptions
- When to use / when not to use guidance
- Composition examples (feature row, settings section)
- Dark mode and prefers-reduced-motion notes

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Add docs-theme.scss with overrides for Storybook's built-in docs
renderer which doesn't respond to our theme toggle. Covers:

Light mode:
- Fix invisible inline code text colour

Dark mode:
- Page background and text colour
- Headings, paragraphs, list items
- Inline code and fenced code blocks with dark backgrounds
- Table rows, headers, and alternating row backgrounds
- Copy button in code blocks
- Horizontal rules and borders

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Separate docs page explaining what skeletons are, when to use them,
how the shimmer animation works (dark mode, reduced motion), variant
reference table, composition examples, and best practices.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Dark mode is verified by toggling the theme in the toolbar — a
dedicated story for it is unnecessary.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…, and proposed components

Three stories under Design System/Typography:
- Current scale: headings, body sizes, and font weights with usage counts
- Known issues: h5 overuse (64x), 49 inline font sizes, no weight tokens,
  fragmented naming
- Proposed components: <Heading> and <Text> with size/weight/colour props
  and polymorphic `as` prop for semantic HTML

This is documentation only — no new components or code changes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…dard size issue

- Add 'Non-standard sizes' to known issues (11px, 13px are off-grid)
- Add proposed base-4 type scale table (12, 14, 16, 18, 24, 30)
  aligned with industry standards (shadcn, Radix, Atlassian, Carbon)
- Update <Text> component proposal to use 12px/14px instead of 13px
- Each proposed token maps to what it replaces

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Four pages under Presentation/ section in Storybook sidebar:
1. Audit Findings — P0/P1/P2 breakdown, findings tables, momentum
2. Competitor Comparison — LaunchDarkly/PostHog/Unleash side-by-side
3. Roadmap — committed work, timeline, future direction
4. The Ask — what we need, definition of success, punchline

These are presentation-specific and should be removed before merging.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Three stories introducing the team to Chromatic and MCP:
- What is Chromatic: publishing, visual regression, review workflow
- What is Storybook MCP: how AI reads component metadata, what it sees
- What this enables: before/after table, virtuous cycle diagram, setup

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Two stories addressing expected pushback:
- Maintenance model: who does what, when, and what doesn't change
- Common questions: 6 FAQ cards covering slowdown concerns,
  adoption, over-engineering, bottleneck prevention, backend
  engineer experience, and the cost of inaction

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Four benefits that come automatically with every story:
- Visual regression testing (Chromatic)
- Accessibility audit (axe-core via a11y addon)
- Living documentation
- AI context via MCP

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Move the four free benefits (visual regression, a11y audit, living
docs, AI context via MCP) from the Maintenance story into its own
sidebar item for easier navigation during the presentation.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…arison

- Reframe 'Competitor Comparison' as 'Industry Validation' with
  'Where we already are' section showing Flagsmith's progress
- Reorder: Chromatic & MCP moves before Roadmap and The Ask so the
  live demo lands right after explaining MCP
- New flow: Audit → Validation → Chromatic/MCP → DEMO → Roadmap → Ask → FAQ

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Storybook forces rendering in isolation — if a component can't render
without the full app, it's too coupled. We already found this with
Setting, Tabs, and CategoricalPalette which imported the Redux store
transitively and couldn't render in Storybook.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Changed '5 purples' to '5 different shades of our brand purple
scattered across the codebase' for clarity.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- P0: 3 parallel theming mechanisms (.dark, getDarkMode, data-bs-theme)
  that semantic tokens will unify
- P1: 280+ hardcoded hex values in TSX not tied to any token
- New Accessibility section: secondary text below WCAG AA, no a11y CI

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…y-changed

Explain that Chromatic only runs on frontend changes (CI path filters)
and skips unchanged stories (--only-changed flag) to minimise snapshot
consumption.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Remove files superseded by the renumbered versions
(03-ChromaticAndMCP, 04-Roadmap, 05-TheAsk).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Restructure feedback tokens from standalone categories
(--color-danger-*, --color-success-*) to element-first tokens
within each category (--color-text-danger, --color-surface-danger,
--color-border-danger, --color-icon-danger).

Each token now has one job: text tokens optimised for contrast,
surface tokens for subtle backgrounds, border and icon tokens
for their specific context.

New categories added:
- Icon: default, secondary, disabled + feedback variants
- Surface: feedback variants (danger, success, warning, info)
- Text: feedback variants
- Border: feedback variants

Also adds common/theme/tokens.ts for JS/TS access to tokens
(for chart libraries, inline SVG fills, runtime colour logic).

Updates Banner component to use new token names.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- --color-text-disabled: greyed out labels, disabled button text
- --color-border-disabled: disabled input/control borders
- --color-icon-disabled: greyed out icons in disabled controls
- --color-icon-secondary: secondary emphasis icons

Light and dark mode values included. JS/TS tokens updated.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…ructure

- Replace 'Feedback' category with 'Icon' category in the table
- Update all categories to mention feedback variants within them
- Update naming convention: category is now element type (surface, text,
  border, icon), variant includes feedback (danger, success, etc.)
- Update code examples to show element-first tokens
  (--color-surface-danger, --color-text-danger, --color-border-danger)
- Update common mistakes: warn against using one token for multiple
  element types

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Brand is not an element type — it's a colour meaning. In the
element-first model, brand purple becomes 'action' within each
category:
- --color-surface-action (button bg, replaces --color-brand-default)
- --color-surface-action-hover, action-active, action-subtle, action-muted
- --color-text-action (link text, CTA text)
- --color-border-action (focused input border)
- --color-icon-action (interactive icon fill)

Four pure element categories remain: Surface, Text, Border, Icon.

Also renames Patterns/Setting to Patterns/SettingRow in Storybook.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…okens

Extend the design token system beyond colour to cover the full taxonomy.
Values align with existing _variables.scss to enable gradual migration.
CSS custom properties are the single source of truth — both SCSS and
future Tailwind config will consume them via var().

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Update from '3 icons' to '~35 icons across 42 files' to reflect
actual codebase usage discovered during issue verification.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

… and maintenance guide

Each story includes visual previews and usage descriptions that
Storybook MCP exposes to AI agents — token intent, pairing rules,
and when-to-use guidance. The maintenance guide documents how to
add, modify, or remove tokens across the system.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Rename --space-100/200/400 to --space-1/2/4 etc. so token names
map directly to Tailwind utility classes (p-4 = var(--space-4) = 16px).
No mental translation between naming systems.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>